Fixex #4256

To solve the related issue, we suggest the user to use these 2 parameters:

db.logs.query.obfuscate_literals=true
db.logs.query.parameter_logging_enabled=false

and he agrees with the tip.

In any case, even with these changes, we still need to handle some errors correctly.

Added a custom exception to obfuscate in logs and the returning RuntimeException,
since the connection string may contain the password.

Therefore, executing:

CALL apoc.load.jdbc("jdbc:notexistent://localhost:3306/data_mart?user=root&password=root","products")

the following exception (and log) will be returned:

java.sql.SQLException:
No suitable driver found for jdbc:notexistent://***

instead of the previous one:

java.sql.SQLException:
No suitable driver found for jdbc:notexistent://localhost:3306/data_mart?user=root&password=root